@jeffhandley if this is required infrastructure flow it can be marked as approved

As far as I can tell, all the failing checks are unrelated to updating arcade. These are all known:

• [6.0] GC test failures: Handle collector count overflows or underflows #81383
• [browser] Connection refused in 127.0.0.1 #104349
• [6.0] Test failure in System.Formats.Asn1 ReadVeryLongOid_WithAppContext: could not load file or assembly in NET48 #104647
• System.IO.Net5Compat.Tests and System.IO.Tests suddenly exiting with error 137 #100558

I don't know how to diagnose the System.IO.Tests failures though, especially where the log merely contains the following:

Console log: 'System.IO.Tests' from job 2b582a72-5bb9-4cbf-afee-c09f36848afe (ubuntu.2204.amd64.open.svc) using docker image mcr.microsoft.com/dotnet-buildtools/prereqs:debian-11-helix-amd64 on a005PK4
running $HELIX_CORRELATION_PAYLOAD/scripts/8e3a716358cf46faa8eb11673920d6f8/execute.sh in /datadisks/disk1/work/B6FF0A3F/w/B2CB09DA/e max 900 seconds

@lewing browser tests failing without known issue.

Everything appears to be like this:

Connection refused [::ffff:127.0.0.1]:41031 (localhost:41031)
[01:27:55] warn: Failed to start the browser, attempt #0: OpenQA.Selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
                   (unknown error: DevToolsActivePort file doesn't exist)
                   (The process started from chrome location /datadisks/disk1/work/A45A094F/p/chrome-linux/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.UnpackAndThrowOnError(Response errorResponse)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
                    at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
                    at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)
                    at OpenQA.Selenium.Chromium.ChromiumDriver..ctor(ChromiumDriverService service, ChromiumOptions options, TimeSpan commandTimeout)
                    at OpenQA.Selenium.Chrome.ChromeDriver..ctor(ChromeDriverService service, ChromeOptions options, TimeSpan commandTimeout)

Seems similar to #43955

@ilonatommy please take a look the the selenium failures here in release/6.0 they don't appear to be related to this change

CI is green!

Nevermind! It never ran.

Looks like this is ready, but has a conflict to resolve. Conflicts with #106725. I propose we solve that and fast merge to get the builds going. @lewing can you help resolve? I'm not sure which feed to take - or do we keep all of them and if so in what order?

I fixed the emsdk feed conflict the same way we were told to fix them whenever we see them (which is quite often): Keep them all (just remove the duplicates). Eventually they get automatically cleaned up by maestro.

We need to take this to unblock servicing.